Skip to content

Don't count spilled memory when comparing vs. process memory#7430

Merged
crusaderky merged 1 commit into
dask:mainfrom
crusaderky:warn_high_managed_memory
Dec 22, 2022
Merged

Don't count spilled memory when comparing vs. process memory#7430
crusaderky merged 1 commit into
dask:mainfrom
crusaderky:warn_high_managed_memory

Conversation

@crusaderky

Copy link
Copy Markdown
Collaborator

Fix regression introduced in #7419, which causes the worker log to be inundated with warnings when heavily spilling.

@crusaderky crusaderky self-assigned this Dec 22, 2022

@mrocklin mrocklin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No objections or strong thoughts from me. Merge at will.

@github-actions

Copy link
Copy Markdown
Contributor

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       22 files  ±  0         22 suites  ±0   10h 1m 36s ⏱️ + 11m 20s
  3 278 tests +  1    3 192 ✔️ +  6       85 💤  - 1  1  - 4 
35 990 runs  +12  34 469 ✔️ +12  1 520 💤 +4  1  - 4 

For more details on these failures, see this check.

Results for commit 0b0d368. ± Comparison against base commit 35c07cb.

@crusaderky crusaderky merged commit d87cea9 into dask:main Dec 22, 2022
@crusaderky crusaderky deleted the warn_high_managed_memory branch December 22, 2022 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants